@scottalanmiller said in How to Install PHP 7.3 on Ubuntu 18.04:

I hate having to do this, but sometimes it has to be done. Here is how to get this middling PHP version onto this old version of Ubuntu.

sudo add-apt-repository ppa:ondrej/php sudo apt update

I'm not sure that is the proper way to do it.
ppa are personal repositories - meaning someone put it together.

I think Ubuntu has offical backports, just like Debian.
In that case it would be better to get a the "newer" php version from the backport repository instead.

UPDATE.
It looks like the ondrej/php repository is actually maintained by a Debian developer, Ondřej Surý. He is one of the package maintainers for the official debian and ubuntu php packages.
https://deb.sury.org/

You can trying using auditd to audit the file.

sudo apt-get install auditd

Running sudo auditctl -l by default show no rules

Create a temporary rule to audit changes to index.php

sudo auditctl -w /var/www/html/index.php -p rwxa # -p = read, write, execute, attributes

Run sudo auditctl -l will show the rule that was created.
Now run sudo ausearch -f index.php | more to show what's touching index.php
or sudo tail -f /var/log/audit/audit.log | grep index.php.

@scottalanmiller said in NextCloud: Unrecoverablely broken?:

Bottom line, in NextCloud you shouldn't be looking at the files from the command line, ever. Not NextCloud files anyway. Permissions are meant to be handled by the app and it's database, not by the filesystem.

Well mostly. Nextcloud needs the files to have the right system permissions.

But user permissions have nothing to do with system permissions.

Also, for a few specific instances, I do quite a bit with Nextcloud files on the command line. But that is a very specific use case, and also has nothing to do with group or share permissions.

Turns out I had a snapshot, restoring it and then regrouping...

Thanks for adding more technical content!

@marcinozga said in Chromium memory usage:

@travisdh1 said in Chromium memory usage:

@marcinozga said in Chromium memory usage:

lynx.PNG

Lynx, 1 tab open :face_with_tears_of_joy:

But why as root?

Root is the only user on that server, no need for any additional accounts.

pB43k.jpg

@scottalanmiller said in Making an RDP Terminal Server with Ubuntu Linux:

I recommend the Remmina RDP client tool, it's the bomb.

I love Remmina as a client.

@Emad-R said in Install OpenVas9 in Ubuntu Server:

@dbeato

the thing is openvas versions is all over the place, dont they have a new version 10 right now, a month ago it was on 8 .

It was 8 then 9 and the 10 version is GVM. I am testing it still but hasn’t been stable for me yet.

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

@matteo-nunziati said in Tracking Down Ubuntu BASH Session Closing:

@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:

If I use zsh, I'm good. If I enter BASH from zsh, I get kicked out after several seconds. Definitely is something to do with BASH.

Stupid tryout: use bash and then enter zsh before being kicked out. Still out?
To understand if it is the firing of bash itself or the stay in bash...

No, the underlying bash remains until the ZSH closes. Same as if you were running top from it, for example.

So basically bash is able to run long running jobs with your user...
It's the interactivity with the shell to be broken... Meh.

Sorry the thread is long, did you mention any test from zsh with:

Bash <-- ok this kills the session
Bash -i any difference???
Bash -l ???
bash --norc
bash --noprofile

From bashman page

For Fedora you can just do

sudo dnf install vagrant-libvirt

And it should be noted, that unlike SMB or NFS shares that would be generally frowned upon to use over the Internet, SFTP is heavily encrypted and very secure and is often used over public networks.

@IRJ said in How to configure automatic updates on Ubuntu 18.04 LTS:

Scripted a bit for anyone interested

FWIW, this line didn't work for me --

sed -i '/Unattended-Upgrade::Skip-Updates-On-Metered-Connections "true"/a\\ "${distro_id}:${distro_codename}-updates"; ' /etc/apt/apt.conf.d/50unattended-upgrades

I believe this is due to the line being inserted outside the Unattended-Upgrade::Allowed-Origins grouping.

@Emad-R said in Ubuntu: history -c doesn't clear:

@gjacobse

you can disable history all together if you want,

https://www.cyberciti.biz/faq/disable-bash-shell-history-linux/

Thank you, I have seen that. But I use history as a track of what I have installed and how I did it. I clear it periodically once I have exported it to a text file.

I do this also to share with my brother - as he's asked me how I've done something a number of times.

@scottalanmiller said in Ubuntu: System Program Problem detected:

That's a desktop pop up, but Ubuntu 18.04 LTS. Why the combination of old Ubuntu, but a desktop?

Why 18.04 -

Well,.. very long obtuse story cut short. having re-installed Ubuntu a time or two due to software / boot issues, I hadn't upgraded to 'save time and stress.' I felt not push to upgrade to 18.10 if I had to yet again kill and install the system. However, things appear stable - so upgrading currently.

I do see on the article, that the crashes could be past - and as such, i can delete the files (several days old) and move on.

@dafyre said in Running Xrdp on Ubuntu:

Not sure what to do about the EFI issue....

What I do when I want to use mine like that is set up x11vnc-server and then run it through XRDP (and choose the console option). It's faster than stock VNC... Don't ask me why, lol. I haven't gotten instructions for that yet, I don't think.

If I remember right, after a reboot, you have to connect, close the connection, and then reconnect back using the XRDP+VNC option. I don't have any installation instructions for that setup on hand though. I can work it out and post them if you like.

This is likely where I went 'rouge' in that I didn't use x11vnc-server.. I had notes on that,.. at least I believe and have misplaced them. so I had forget that.

As I was starting to have other 'OS' Kernel issues (the mouse and keyboard wasn't working correctly) I nuked that partition from Windows, and will rebuild. Maybe it'll survive as I am of course getting grub 'errors' since that partition is gone.

@JaredBusch said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:

@Dashrender said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:

@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:

Windows DUMBASS-ory..

Talking to my brother, he mentioned some 'issues' with Windows not releasing the lock on the partition. He suggested and this is the really dumb part on windows.

To boot Windows and RESTART normally.

Since grub starts Ubuntu by default, it booted normally into Ubuntu.

I did the lsblk -f as before, only this time for /dev/sda4 - there is a UID for it. AND it shows as NTFS..

so,.. FFS Windows,.. FYS. now,.. to see how to prevent this stupidness in the future.

This why someone suggested that you go into Windows and do a full shutdown with shift shutdown.... normal shutdowns now aren’t full shut downs to allow the system to boot faster.

But he did that and it made no difference

Yup - a FULL shutdown didn't do anything more that the SHIFT shutdown.